Add support for custom SignalR hubs #2091
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A start at allowing custom hubs in Wolverine.
Tested using the WolverineChat sample project.
Basically do
opts.UseSignalR<MyCustomHub>andapp.MapWolverineSignalRHub<MyCustomHub>()where
MyCustomHubinherits fromWolverineHub. The old extensions forUseSignalRandMapWolverineSignalRHubremains and uses the defaultWolverineHubI made
WolverineHub.ReceiveMessagevirtual to allow customization as well.(And hopefully people remember to call
base.ReceiveMessageas well...)There's still no support for a hub that uses
[Authorize]or has other ways of authenticating.I was planning on looking into that later.